garmin_fit: implement enhanced speed and enhanced altitude
authorMarco Leogrande <dark.knight.ita@gmail.com>
Thu, 22 Jun 2017 06:04:57 +0000 (23:04 -0700)
committerMarco Leogrande <dark.knight.ita@gmail.com>
Tue, 27 Jun 2017 04:07:41 +0000 (21:07 -0700)
Add handling for fields 73 (enhanced_speed) and 78 (enhanced_altitude)
under global ID 20. Their value is handled exactly the same way as
speed (field 6) and altitude (field 2), except that they have larger
width.

garmin_fit.cc

index 9d7db66f0c30e42c2cc5fab4aeb652c69641145f..57c8a2a1fea8b08d5972f2ab86eee2e632ae00d3 100644 (file)
@@ -411,6 +411,18 @@ fit_parse_data(fit_message_def* def, int time_offset)
           }
           temperature = val;
           break;
+        case 73:
+          if (global_opts.debug_level >= 7) {
+            debug_print(7,"%s: parsing fit data: enhanced_speed=%d\n", MYNAME, val);
+          }
+          speed = val;
+          break;
+        case 78:
+          if (global_opts.debug_level >= 7) {
+            debug_print(7,"%s: parsing fit data: enhanced_altitude=%d\n", MYNAME, val);
+          }
+          alt = val;
+          break;
         default:
           if (global_opts.debug_level >= 1) {
             debug_print(1, "%s: unrecognized data type in GARMIN FIT record: f->id=%d\n", MYNAME, f->id);